|
In distributed computing, code mobility is the ability for running programs, code or objects to be migrated (or moved) from one machine or application to another.〔 This is the process of moving ''code'' across the nodes of a network as opposed to distributed computation where the ''data'' is moved. It is common practice in distributed systems to require the movement of code or processes between parts of the system, instead of data. Examples of code mobility include scripts downloaded over a network (for example JavaScript, VBScript), Java applets, ActiveX controls, Flash animations, Shockwave movies (and Xtras), and macros embedded within Microsoft Office documents. ==Overview== The purpose of code mobility is to support sophisticated operations. For example an application can send an object to another machine, and the object can resume executing inside the application on the remote machine with the same state as it had in the originating application. ;Code mobility can be either ''Strong'' or ''Weak'':〔 * Strong code mobility involves moving the code, data ''and'' the execution state from one host to another. This is important in cases where the running application needs to maintain its state as it migrates from host to host. * Weak code mobility involves moving the code and the data only. This may necessitate restarting the execution of the program at the destination host. ;Several paradigms, or ''architectural styles'', exist within code mobility:〔 * Remote evaluation — A client sends code to a remote machine for execution. * Code on demand — A client downloads code from a remote machine to execute locally. * Mobile agents — Objects or code with the ability to migrate between machines autonomously. 抄文引用元・出典: フリー百科事典『 ウィキペディア（Wikipedia）』 ■ウィキペディアで「code mobility」の詳細全文を読む スポンサード リンク
|